Methods and systems for a universal wireless platform for asset monitoring

ABSTRACT

A metrological interface device includes a printed circuit board (“PCB”) including at least one metrological sensor communication interface and at least one first wireless communication interface. The metrological interface device is in communication with a metrological sensing device via the metrological sensor communication interface. Each metrological sensing device is coupled to a physical asset. Each metrological interface device is configured to receive the metrological data from the metrological sensing device. The metrological interface device is configured to receive metrological data from the metrological sensing device via the metrological sensor communication interface. Metrological data represents physical measurement data associated with the physical asset. Each metrological interface device is configured to advertise connection availability to a plurality of mobile computing devices, and also configured to receive a connection request from a connecting mobile computing device, and is additionally configured to create an active connection with the connecting mobile computing device.

BACKGROUND

The field of the disclosure relates generally to an apparatus,computer-implemented system, and computer-implemented method used tocreate a universal wireless platform for asset monitoring which may beused in the monitoring of physical assets and physical systems.

Many known physical assets and physical systems require assetmonitoring. Asset monitoring may involve the determination of assetstatus by identifying asset data including, for example, physicalmeasurements related to assets or asset components, physical location ororientation of assets, and the presence or physical availability ofassets. Reliable asset data may be obtained using metrologicalinspection. As used herein, “metrological inspection” refers to the useof devices or tools to obtain asset data and, in particular, physicalmeasurements. Asset data may describe physical measurements including,for example and without limitation, distance, volume, pressure, andvelocity. Alternatively, asset data may describe asset characteristicswhich require analysis or extrapolation to determine physicalmeasurements. For example, asset data may be optical data which includesa plurality of geographic coordinates in reference to an asset. Theoptical data may not be immediately discernible as useful physicalmeasurements but computation and extrapolation may yield physicalmeasurements. Metrological inspection may involve the use ofmetrological inspection devices. Metrological inspection devices mayinclude any device capable of facilitating metrological inspectionincluding, for example, gauges, sensors, and calipers. Some knownmetrological inspection devices may include computing devices capable ofdisplaying asset data to a user display (e.g., a liquid-crystal display)and storing asset data to a memory device. Some computing devicesincluded with metrological inspection devices may additionally be ableto transmit asset data to other computing devices. The computing devicesthat are capable of transmitting asset data to other computing devicesmay utilize a variety of communication protocols to transmit asset data.

Many known physical systems and physical assets are monitored andinspected through taking a large plurality of asset data readings. Suchmonitoring and inspection may be time consuming. Additionally, suitablemonitoring and inspection of such physical systems may requirecomputational capabilities which are not immediately available to fieldinspectors.

BRIEF DESCRIPTION

In one aspect, a computer-implemented system is provided. The systemincludes a plurality of metrological interface devices. The metrologicalinterface device includes a printed circuit board (PCB), also referredto as a circuit card assembly (CCA). The PCB includes at least onemetrological sensor communication interface and at least one firstwireless communication interface. The metrological interface device isin communication with a metrological sensing device via the metrologicalsensor communication interface. The metrological sensing device isconfigured to detect metrological data from a physical asset. Themetrological interface device is configured to receive the metrologicaldata from the metrological sensing device. The system also includes aplurality of mobile computing devices. At least one of the mobilecomputing devices includes a memory device, a processor coupled to thememory device, and a second wireless communication interface coupled tothe memory device and to the processor. The second wirelesscommunication interface is configured to communicate with themetrological interface devices via the first wireless communicationinterface. The mobile computing device is configured to scan foravailable metrological interface devices. The available metrologicalinterface devices are a subset of the plurality of metrologicalinterface devices. The mobile computing device is further configured totransmit a connection request to at least one available metrologicalinterface device. The mobile computing device is also configured tocreate an active connection with at least one available metrologicalinterface device. The mobile computing device is additionally configuredto communicate with at least one connected metrological interfacedevice.

In a further aspect, a computer-based method is provided. Thecomputer-based method is performed by a mobile computing device. Themobile computing device includes a memory device, a processor coupled tothe memory device, and a wireless communication interface capable ofcommunicating with at least one metrological interface device. Themethod includes scanning for available metrological interface deviceswherein said available metrological interface devices are a subset ofplurality of metrological interface devices. The method further includescreating an active connection with the at least one availablemetrological interface device. The method also includes communicatingwith the at least one connecting metrological interface device.

In another aspect, a metrological interface device is provided. Themetrological interface device includes a printed circuit board (“PCB”)including at least one metrological sensor communication interface andat least one first wireless communication interface. The metrologicalinterface device is in communication with a metrological sensing devicevia the metrological sensor communication interface. The metrologicalsensing device is coupled to a physical asset. The metrologicalinterface device is configured to receive the metrological data from themetrological sensing device. The metrological interface device isconfigured to receive metrological data from the metrological sensingdevice via the metrological sensor communication interface. Metrologicaldata substantially represents physical measurement data associated withthe physical asset. The metrological interface device is furtherconfigured to advertise connection availability to a plurality of mobilecomputing devices. The metrological interface device is also configuredto receive a connection request from a connecting mobile computingdevice. The metrological interface device is additionally configured tocreate an active connection with the connecting mobile computing device.

DRAWINGS

These and other features, aspects, and advantages will become betterunderstood when the following detailed description is read withreference to the accompanying drawings in which like charactersrepresent like parts throughout the drawings, wherein:

FIG. 1A is an illustration of an environment containing physical assetsbeing monitored by field inspectors without using metrological sensingdevices and further without using the universal wireless platformdescribed in the present disclosure;

FIG. 1B is an illustration of an environment containing physical assetsbeing monitored by field inspectors using metrological sensing devicesbut without using the universal wireless platform described in thepresent disclosure;

FIG. 1C is an illustration of an environment containing physical assetsbeing monitored by field inspectors using metrological sensing devicesand using a universal wireless platform;

FIG. 2 is a block diagram of an exemplary metrological interface devicefor use in creating a universal wireless platform to facilitate themonitoring of the example environment shown in FIG. 1B;

FIG. 3A is an illustration of an exemplary fob device containingmetrological interface device shown in FIG. 2 used to create a universalwireless platform;

FIG. 3B is an illustration of an example hybrid device containingmetrological interface device shown in FIG. 2 used to create a universalwireless platform;

FIG. 4 is a block diagram of a computing device used in monitoringassets by interacting with the metrological interface device shown inFIG. 2 through the universal wireless platform;

FIG. 5 is an exemplary process flow of a system implemented by themobile computing device shown in FIG. 4 interacting with a metrologicalsensing device using the universal wireless platform and, morespecifically, the metrological interface device shown in FIG. 2;

FIG. 6 is an exemplary process flow of a system implemented by themobile computing device shown in FIG. 4 interacting with a metrologicalsensing device using the universal wireless platform and, morespecifically, the metrological interface device shown in FIG. 2 tofacilitate efficient asset data collection, asset monitoring, and assetinspection;

FIG. 7 is an exemplary method performed by the mobile computing deviceshown in FIG. 4 communicating with the metrological interface deviceshown in FIG. 2 using the universal wireless platform;

FIG. 8 is an exemplary method performed by the mobile computing deviceshown in FIG. 4 communicating with the metrological interface deviceshown in FIG. 2 and a plurality of cloud based resources using theuniversal wireless platform; and

FIG. 9 is a diagram of components of one or more example computingdevices that may be used in the environment shown in FIGS. 5 and 6.

Unless otherwise indicated, the drawings provided herein are meant toillustrate features of embodiments of the disclosure. These features arebelieved to be applicable in a wide variety of systems comprising one ormore embodiments of the disclosure. As such, the drawings are not meantto include all conventional features known by those of ordinary skill inthe art to be required for the practice of the embodiments disclosedherein.

DETAILED DESCRIPTION

In the following specification and the claims, reference will be made toa number of terms, which shall be defined to have the followingmeanings.

The singular forms “a”, “an”, and “the” include plural references unlessthe context clearly dictates otherwise.

“Optional” or “optionally” means that the subsequently described eventor circumstance may or may not occur, and that the description includesinstances where the event occurs and instances where it does not.

As used herein, the term “non-transitory computer-readable media” isintended to be representative of any tangible computer-based deviceimplemented in any method or technology for short-term and long-termstorage of information, such as, computer-readable instructions, datastructures, program modules and sub-modules, or other data in anydevice. Therefore, the methods described herein may be encoded asexecutable instructions embodied in a tangible, non-transitory, computerreadable medium, including, without limitation, a storage device and/ora memory device. Such instructions, when executed by a processor, causethe processor to perform at least a portion of the methods describedherein. Moreover, as used herein, the term “non-transitorycomputer-readable media” includes all tangible, computer-readable media,including, without limitation, non-transitory computer storage devices,including, without limitation, volatile and nonvolatile media, andremovable and non-removable media such as a firmware, physical andvirtual storage, CD-ROMs, DVDs, and any other digital source such as anetwork or the Internet, as well as yet to be developed digital means,with the sole exception being a transitory, propagating signal.

As used herein, the term “asset data” and related terms refers to anydata related to at least one physical state of at least physical asset.Asset data may include, without limitation, physical measurements ofdistance, physical measurements of volume, physical measurements ofpressure, physical measurements of temperature, location information,physical measurements of electrical current, and any other physicalmeasurements which may be detected using a metrological sensing device.Asset data containing physical measurements may be referred to as“primary asset data.” Alternately, asset data may include, withoutlimitation, “secondary asset data” which may be used to determinephysical measurements. For example, optical data produced by a borescopemay present as a series of three-dimensional coordinates which can beprocessed to determine the physical characteristics of an asset.However, such optical data may not represent “primary asset data” withinthe meaning above unless such processing occurs. As used herein, thisform of secondary asset data used to create physical measurements may beused interchangeably with primary asset data containing physicalmeasurements, unless otherwise noted.

As used herein, the term “metrological sensing device” and related termsrefers to tools, device, and other apparatus capable of measuring orotherwise determining asset data. Although metrological sensing devicesmay be manual or electronic, the metrological sensing devices used inconjunction with the systems and methods described herein are capable oftransmitting asset data to a computing device. In some examples,metrological sensing devices may include a display, a processor, and amemory device. Additionally, metrological sensing devices may produceanalog data and digital data. In at least some examples, metrologicalsensing devices may produce complex data which requires computation todecode into physical measurement data (or primary asset data, asdescribed above).

As used herein, the terms “software” and “firmware” are interchangeable,and include any computer program stored in memory for execution bydevices that include, without limitation, mobile devices, clusters,personal computers, workstations, clients, and servers.

As used herein, the term “computer” and related terms, e.g., “computingdevice”, are not limited to integrated circuits referred to in the artas a computer, but broadly refers to a microcontroller, a microcomputer,a programmable logic controller (PLC), an application specificintegrated circuit, and other programmable circuits, and these terms areused interchangeably herein.

As used herein, the term “cloud computing” and related terms, e.g.,“cloud computing devices” refers to a computer architecture allowing forthe use of multiple heterogeneous computing devices for data storage,retrieval, and processing. The heterogeneous computing devices may use acommon network or a plurality of networks so that some computing devicesare in networked communication with one another over a common networkbut not all computing devices. In other words, a plurality of networksmay be used in order to facilitate the communication between andcoordination of all computing devices.

As used herein, the term “mobile computing device” refers to any ofcomputing device which is used in a portable manner including, withoutlimitation, smart phones, personal digital assistants (“PDAs”), computertablets, hybrid phone/computer tablets (“phablet”), or other similarmobile device capable of functioning in the systems described herein. Insome examples, mobile computing devices may include a variety ofperipherals and accessories including, without limitation, microphones,speakers, keyboards, touchscreens, gyroscopes, accelerometers, andmetrological devices. Also, as used herein, “portable computing device”and “mobile computing device” may be used interchangeably.

Approximating language, as used herein throughout the specification andclaims, may be applied to modify any quantitative representation thatcould permissibly vary without resulting in a change in the basicfunction to which it is related. Accordingly, a value modified by a termor terms, such as “about” and “substantially”, are not to be limited tothe precise value specified. In at least some instances, theapproximating language may correspond to the precision of an instrumentfor measuring the value. Here and throughout the specification andclaims, range limitations may be combined and/or interchanged, suchranges are identified and include all the sub-ranges contained thereinunless context or language indicates otherwise.

The computer-implemented systems and methods described herein facilitatethe creation of a universal wireless platform for asset monitoring whichmay be used in the monitoring of physical assets and physical systems.The systems and methods provide the universal wireless platform byproviding a standard interface from metrological sensing devices tocomputing devices including mobile computing devices. The standardinterface allows a variety of metrological sensing devices to transmitasset data to computing devices and thereby facilitates processing assetdata efficiently. Specifically, by standardizing this communication, theuniversal wireless platform allows a significant reduction in theresources and investment required to monitor and inspect physicalassets. Additionally, this platform resultantly effects rapid conditionmonitoring and inspection of physical assets.

The computer-implemented systems and methods described herein furtherfacilitate dynamic workflow processing in the collection, review, andprocessing of asset data. Using the universal wireless platform, thesystems and methods facilitate responsive asset data collection tocapture asset data relevant to determining a data model of the physicalstate of at least one asset. The systems and methods also facilitatecloud-based processing and determinations of a new data model of thephysical state of the at least one asset. The new data models andcollected asset data can further be transmitted locally and across anetwork to other computing devices to determine potential reactive stepsincluding further diagnosis, maintenance, and repair of physical assets.

FIG. 1A is an illustration of an example environment 100 containingphysical assets 140 being monitored by field inspectors 111, 112, 113,and 114 without using metrological sensing devices (not shown in FIG.1A) and accordingly without using the universal wireless platformdescribed in the present disclosure. Environment 100 is an exampleillustration showing the complexities of monitoring and inspectingphysical assets 140. In the exemplary embodiment, environment 100 is achemical processing facility containing physical assets 140 used toprocess industrial chemicals. Although environment 100 includes fourrows of physical assets 151, 152, 153, and 154 used in the chemicalprocessing facility, the systems and methods described herein may beapplied to any environment 100 containing any number or variety ofphysical assets 140 including, without limitation, industrialenvironments, power generation and distribution environments,manufacturing environments, biotechnology environments, commercial salesenvironments, commercial distribution environments, transportationenvironments, residential environments, and agricultural environments.

Environment 100 includes a plurality of field inspectors 111, 112, 113,and 114 monitoring physical assets 140. Field inspectors 111, 112, 113,and 114 use a plurality of measurement devices 121, 122, 123, and 124 totake physical measurements and obtain asset data (i.e., primary assetdata) from physical assets 140. More specifically, the field inspectoris using a particular tool. For example, field inspector 111 is usingcaliper 121 to measure widths of cracks in physical asset row 151. Fieldinspector 112 is using a pressure gauge to measure pressure levels ofvessels in physical asset row 152. Field inspector 113 is using levelgauge 123 to determine the level of fluids in vessels of physical assetrow 153. Field inspector 114 is using temperature gauge 124 to measurethe temperature of vessels of physical row 154. Because the fieldinspector is only obtaining a specific type of measurements, they eachneed to take measurements from all four physical asset rows 151, 152,153, and 154. Although each field inspector could have more measurementdevices, each asset measurement must be taken manually.

Field inspectors 111, 112, 113, and 114 further record asset data. Fieldinspectors 111 and 112 manually record asset data into paper records 131while field inspectors 113 and 114 electronically record asset data intomobile computing devices 132. However, once all asset data has beenrecorded, the asset data still has to be consolidated to properlymonitor environment 100. Asset data is consolidated on monitoring server180. Each field inspector 111, 112, 113, and 114 must provide asset datarecorded in paper records 131 or mobile computing devices 132. Fieldinspectors 111 and 112 may use a recording computing device 181 to enterasset data into a record. Field inspectors 113 and 114 may use recordingcomputing device 181 to enter asset data or alternately use mobilecomputing devices 132 to directly transmit asset data to monitoringserver 180. Recording computing device 181 may transmit asset data tomonitoring server 180.

As is shown, the process of obtaining asset data, recording asset data,and consolidating asset data may be very time consuming for fieldinspectors 111, 112, 113, and 114. As described below, usingmetrological sensing devices and further using the universal wirelessplatform described herein can expedite the process of the monitoring ofphysical assets 140.

FIG. 1B is an illustration of an example environment 100A containingphysical assets 140 being monitored by field inspectors 111, 112, 113,and 114 using metrological sensing devices 161, 163, 164, and 165 butwithout using the universal wireless platform described in the presentdisclosure. As in FIG. 1, environment 100A is a chemical processingfacility containing physical assets 140 used to process industrialchemicals. In environment 100A, field inspectors 111, 112, 113, and 114utilize mobile computing devices 132 to record asset data. Additionally,unlike in FIG. 1A, physical assets 140 have at least one of metrologicalsensing devices 161, 163, 164, and 165 physically attached to each assetof physical assets 140.

Although in environment 100A, metrological sensing devices 161, 163,164, and 165 are physically coupled to a physical asset of physicalassets 140, not all metrological sensing devices 161, 163, 164, and 165may be physically coupled to physical assets 140. Depending on at leastthe size, portability, cost and scarcity of each metrological sensingdevices 161, 163, 164, and 165, metrological sensing devices 161, 163,164, and 165 may be removable and/or portable from physical assets 140.

Metrological sensing devices 161, 163, 164, and 165 are configured toobtain at least one kind of asset data. For example metrological sensingdevice 161 is sensing device configured to take measurements equivalentto a caliper. Metrological sensing device 163 is configured to takepressure measurements. Metrological sensing device 163 is physicallycontained within housing 162. Metrological sensing device 164 isconfigured to take fluid level measurements. Metrological sensing device165 is configured to take temperature readings. Alternately,metrological sensing devices 161, 163, 164, and 165 may obtain any kindof asset data as described above. More specifically, calipermeasurements, pressure measurements, fluid level measurements, andtemperature readings may be described as primary data as each is a formof asset data including physical measurements. In contrast, metrologicalsensing devices 161, 163, 164, and 165 may alternately collect secondarydata which may be processed into primary data.

In some embodiments, metrological sensing devices 161, 163, 164, and 165include output interfaces allowing each metrological sensing device totransmit asset data to at least some computing devices. Metrologicalsensing devices 161, 163, 164, and 165 may use a variety ofcommunications protocols to transmit asset data via their respectiveoutput interfaces including, for example, universal serial bus (“USB”),recommended standard 232 (“RS232”), serial peripheral interface bus(“SPI”), inter-integrated circuit (“I2C”), analog, and proprietary I/Ointerfaces. Dozens of proprietary I/O interfaces exist which requirespecific methods of interaction to obtain asset data. Accordingly,mobile computing device 132 may send and receive data from and tometrological sensing devices 161, 163, 164, and 165 if mobile computingdevice 132 and metrological sensing devices 161, 163, 164, and 165support the same communications protocols. Accordingly, although mobilecomputing device 132 may be capable of receiving data using at leastsome of these communications standards, some standards may not besupported by a particular mobile computing device 132. In the exemplaryembodiment, metrological sensing device 161 uses a USB input/outputinterface, metrological sensing device 163 uses a RS232 input/outputinterface, metrological sensing device 164 uses a first proprietaryinput/output interface, and metrological sensing device 165 uses asecond input/output interface. In the exemplary embodiment, mobilecomputing device 132 supports USB and I2C. Accordingly, field inspectors111, 112, 113, and 114 can only receive digital output from metrologicalsensing device 161. All other asset data from metrological sensingdevices 163, 164, and 165 require manual input into mobile computingdevices 132.

Metrological sensing devices 161, 163, 164, and 165 allows fieldinspectors 111, 112, 113, and 114 to monitor and inspect physical assets140 more efficiently than in environment 100 but there are stilllimitations which prevent efficient capture and processing of assetdata. As described above, the variety of communications standardsemployed by metrological sensing devices 161, 163, 164, and 165 mayforce each field inspector 111, 112, 113, and 114 to manually inputasset data for at least some metrological sensing devices 161, 163, 164,and 165. Additionally, where metrological sensing devices 161, 163, 164,and 165 use communications standards supported by mobile computingdevice 132, each field inspector must physically connect to anymetrological sensing device 161, 163, 164, and 165 which does notsupport a wireless communication protocol. Such connection may requireadditional equipment (e.g., wires or cables) and take additional time.Also, field inspectors 111, 112, 113, and 114 must consolidate the assetdata obtained at monitoring server 180 as in FIG. 1A.

FIG. 1C is an illustration of an example environment 100B containingphysical assets 140 being monitored by field inspectors 111, 112, 113,and 114 using metrological sensing devices 161, 163, 164, and 165 andusing a universal wireless platform. In environment 100B, eachmetrological sensing device is coupled to a metrological interfacedevice 170. In the exemplary embodiment, metrological interface device170 represents a printed circuit board (“PCB”) capable of receivingasset data using a plurality of communication protocols including USB,RS232, I2C, SPI, analog, and proprietary I/O protocols.

Communication to each metrological sensing device using each respectivecommunication protocol requires interface links 172, 173, 174, and 175.Interface link 172 allows metrological interface device 170 tocommunicate with metrological sensing device 161 using a USB protocol.Interface link 173 allows metrological interface device 170 tocommunicate with metrological sensing device 163 using a RS232 protocol.Interface link 174 allows metrological interface device 170 tocommunicate with metrological sensing device 164 using a firstproprietary input/output protocol. Interface link 175 allowsmetrological interface device 170 to communicate with metrologicalsensing device 165 using a second proprietary input/output protocol.

In one example, metrological interface device 170 is coupled externallyto a metrological sensing device (e.g., metrological sensing device161). In this example, metrological interface device 170 may include achassis to contain metrological interface device. The chassis may bemade of any material including, for example, metal, plastic, a metalalloy, or any other material suitable for containing the PCB andfacilitating interaction between metrological interface device 170 and ametrological sensing device.

In a second example, metrological interface device 170 is containedwithin a chassis containing both a metrological interface device and ametrological sensing device (e.g., housing 162 containing metrologicalsensing device 163 and metrological interface device 170.)

Metrological interface device 170 is further configured to communicatewith mobile computing device 132. In the exemplary embodiment,metrological interface device 170 uses Bluetooth® Low Energy (“BLE”)protocol to communicate with mobile computing device 132. BLE is alsoknown as Bluetooth SMART®. (Bluetooth and Bluetooth SMART are registeredtrademarks of Bluetooth Special Interest Group of Kirkland, Wash.) BLEis an advantageous protocol for metrological interface device 170 to usein generating the universal wireless platform because it consumesrelatively low power while maintaining communication ranges associatedwith Bluetooth. Given the size of at least some environments 100Bmonitored by field inspectors 111, 112, 113, and 114, greater ranges ofcommunication may enable efficient field inspections. Additionally, BLEis a commonly supported wireless protocol for a variety of mobilecomputing devices 132. Using metrological interface device 170 to allowasset data received by metrological sensing devices 161, 163, 164, and165 to be received by mobile computing device 132 substantiallyrepresents creating a universal wireless platform. Accordingly,metrological interface device 170 substantially facilitates the creationand use of the universal wireless platform to facilitate inspection andmonitoring of physical assets 140.

In alternative embodiments, metrological interface device 170 can useadditional wireless protocols including, for example 802.11b, Bluetooth,and ZigBee®. (ZigBee is a registered trademark of the ZigBee Alliance ofSan Ramon, Calif.) Alternately, any other suitable wireless protocol maybe used. In additional embodiments, metrological interface device 170can also provide wired communication using protocols including, withoutlimitation, USB, RS232, I2C, SPI, analog, and proprietary I/O protocols.

Environment 100B allows field inspectors 111, 112, 113, and 114 toobtain asset data in a more efficient manner than illustrated inenvironments 100 or 100A. For example, each field inspector canwirelessly connect to all metrological sensing devices 161, 163, 164,and 165 by using metrological interface device 170. Metrologicalinterface device 170 presents the availability of each metrologicalsensing device to a mobile computing device 132 and allow the requestand transfer of asset data. By facilitating the collection of assetdata, field inspectors 111, 112, 113, and 114 can further transfer assetdata to monitoring server 180. In the exemplary embodiment, monitoringserver 180 also receives asset data from mobile computing devices usingBLE. In alternative embodiments, monitoring server 180 can receive assetdata using any wireless or wired protocol including, for example andwithout limitation, 802.11b and ZigBee®.

In at least some examples, field inspectors 111, 112, 113, and 114receive secondary asset data from metrological sensing devices 161, 163,164, and 165 via at least one metrological interface device 170. Asdescribed above, secondary asset data refers to asset data which doesnot directly describe physical measurements associated with physicalassets 140. Instead, secondary asset data may be processed to determineprimary asset data which describes physical measurements associated withphysical assets 140. Examples of methods of processing methods used toprocess secondary asset data into primary asset data include, withoutlimitation, numerical calculations, numerical analysis, and complexmodeling. Examples of categories of asset data which may requireprocessing into primary asset data include, without limitation, chemicaldata wherein discrete values from chemical sensors may be processed tocreate a chemistry model as primary asset data, and electrical datawherein discrete electrical signals may be processed into electricalmodels as primary asset data.

Processing secondary asset data may require significant computationalpower and therefore a processor (not shown in FIG. 1C) with significantprocessing power. Alternately, processing secondary asset data intoprimary asset data may require the receipt of external data (e.g., datamodels or historic primary asset data) from a data source including, forexample and without limitation, a memory device (not shown in FIG. 1C),a database (not shown in FIG. 1C), or a networked computing device.Accordingly, it may be efficient for secondary asset data to beprocessed into primary asset data by a computing device such as mobilecomputing device 132. Alternately, mobile computing device 132 maytransfer the secondary asset data to a separate computing device (notshown in FIG. 1C) to process the secondary asset data into primary assetdata and, in some examples, receive the processed primary asset datafrom the separate computing device. Functionally, the application of auniversal wireless platform facilitated by metrological interface device170 allows computing devices including mobile computing device 132 tofunction in concert with metrological sensing devices 161, 163, 164, and165 and accordingly makes such computing devices a part of metrologicalsensing devices 161, 163, 164, and 165 in that the computing devicesgenerate primary asset data regarding physical assets 140.

FIG. 2 is a block diagram 200 of an exemplary metrological interfacedevice 170 for use in creating a universal wireless platform tofacilitate the monitoring of the example environment 100B (shown in FIG.1C). Metrological interface device 170 substantially represents aprinted circuit board (“PCB”). Block diagram 200 is laid out toillustrate important functional components of the PCB but block diagram200 should not be construed to present an exhaustive illustration of allcomponents of metrological interface device 170 or a functional layoutof such components. It is noted that metrological interface device 170may alternately be characterized as a printed circuit assembly (“PCA”).As described above, metrological interface device 170 facilitatescommunication between a metrological sensing device, for example,metrological sensing device 161 (shown in FIG. 1C) and mobile computingdevice 132 (shown in FIG. 1C).

In the exemplary embodiment, metrological interface device 170communicates with a metrological sensing device such as metrologicalsensing device 161 using interface link 172. Interface link 172 allowsmetrological interface device 170 to communicate using a plurality ofcommunication protocols including, without limitation, USB, RS232, I2C,SPI, analog, and proprietary I/O protocols. In the exemplary embodiment,interface link 172 connects to a metrological sensing device using SPIprotocol. Metrological interface device 170 facilitates communicationwith metrological sensing devices by using a plurality of communicationsmodules which allow metrological interface device 170 to receive data,including asset data including primary asset data and secondary assetdata, from the metrological sensing devices such as metrological sensingdevice 161. The plurality of communications modules include a USB module212, an RS232 module 213, an analog module 214, an I2C module 215, anSPI module 216, and a generic input/output module 217.

Some metrological sensing devices such as metrological sensing device161 utilize proprietary or customized communication protocols. Thesecommunication protocols may be specific to a vendor of metrologicalsensing device 161 or an external standard. Generic input/output module217 allows for interaction with such proprietary or customizedcommunication protocols. Generic input/output module 217 may beprogrammed to interface with a particular communication protocol using,for example, a firmware installation or upgrade.

In the exemplary embodiment, metrological interface device 170additionally includes a processor 220 and a memory device 225. In theexemplary embodiment, metrological interface device 170 includes asingle processor 220 and a single memory device 225. In alternativeembodiments, metrological interface device 170 may include a pluralityof processors 220 and/or a plurality of memory devices 225. In someembodiments, executable instructions are stored in memory device 225.Metrological interface device 170 is configurable to perform one or moreoperations described herein by programming processor 220. For example,processor 220 may be programmed by encoding an operation as one or moreexecutable instructions and providing the executable instructions inmemory device 225. Alternately, processor 220 may be used to processsecondary asset data into primary asset data.

In the exemplary embodiment, memory device 225 is one or more devicesthat enable storage and retrieval of information such as executableinstructions and/or other data. Memory device 225 may include one ormore tangible, non-transitory computer-readable media, such as, withoutlimitation, random access memory (RAM), dynamic random access memory(DRAM), static random access memory (SRAM), a solid state disk, a harddisk, read-only memory (ROM), erasable programmable ROM (EPROM),electrically erasable programmable ROM (EEPROM), and/or non-volatile RAM(NVRAM) memory. The above memory types are exemplary only, and are thusnot limiting as to the types of memory usable for storage of a computerprogram.

Memory device 225 may be configured to store asset data as describedabove. Asset data may be stored to facilitate data backup, to providemultiple samples of asset data, and to facilitate calibration. Memorydevice 225 may additionally store data models and other data structuresused to process asset data. In the exemplary embodiment, metrologicalinterface device 170 is encoded with firmware which runs at processor220. Firmware for the metrological interface device managescommunication protocols, interface protocols, encryption, data formats,and power management. Firmware may be installed, upgraded, or removedusing over-the-air programming or using a direct interface with acomputing device such as mobile computing device 132.

Metrological interface device 170 further includes BLE module 230. BLEmodule 230 allows metrological interface device 170 to wirelesslycommunicate with computing devices, including mobile computing device132, using the Bluetooth Low Energy® protocol. In the exemplaryembodiment, metrological interface device 170 further includes wirelessmodule 240 allowing metrological interface device 170 to wirelesslycommunicate with computing devices using a wireless protocol including,without limitation, 802.11b and ZigBee®.

Metrological interface device 170 also includes light-emitting diode(“LED”) module 250 which can be used to facilitate displays to a usersuch as field inspector 111 (shown in FIG. 1A). LED module 250 can beused to indicate information related to metrological interface device170 and connected metrological sensing device 161 including, withoutlimitation, power availability, signal strength, connection status, andasset data readouts.

Metrological interface device 170 additionally includes accelerometer260. Accelerometer 260 may be used to determine the frame of referenceof metrological interface device 170. Frame of reference may bedetermined by accelerometer 260 and provided to a computing device suchas mobile computing device 132. Frame of reference data may be used inconjunction with asset data to provide users such as field inspector 111additional data regarding the physical state of an asset. Frame ofreference data may also be used to process secondary asset data intoprimary asset data. Frame of reference data may additionally be receivedby a computing device such as mobile computing device 132 as asset data.Alternately, accelerometer 260 may similarly determine and providevelocity data and any other data which may be generated by anaccelerometer 260.

Metrological interface device 170 additionally includes any standardcomponents and peripherals necessary to facilitate the functionsdescribed including, without limitation, heat sinks or heat dispersalmechanisms, capacitors, transistors, and any other circuitry orcomponents which may be required (not shown in FIG. 2).

In operation, metrological interface device 170 is configured tocommunicate with a metrological sensing device such as metrologicalsensing device 161 using interface link 172. Communications betweenmetrological interface device 170 and metrological sensing device 161follows a communication protocol supported by metrological sensingdevice 161 and is accordingly facilitated by at least one of USB module212, RS232 module 213, analog module 214, I2C module 215, SPI module216, and generic input/output module 217. Metrological interface device170 can accordingly send and receive data to the metrological sensingdevice including asset data. Data including asset data may be stored atmemory device 225.

Metrological interface device 170 also communicates with a computingdevice such as mobile computing device 132. Communications betweenmetrological interface device 170 and the computing device isfacilitated by at least one of BLE module 230 and wireless module 240.Processor 220 runs functions including firmware functions to managecommunication protocols, process asset data from secondary asset datainto primary asset data, manage interface protocols, manage encryption,manage data formats, and manage power and other resources.

In alternative embodiments, metrological interface device 170 mayinclude any combination of components and modules indicated in FIG. 2.In some embodiments, metrological interface device 170 may includeadditional components and modules to facilitate the system and methoddescribed herein.

FIG. 3A is an illustration of an exemplary fob device 300 containingmetrological interface device 170 (shown in FIG. 2) and used to create auniversal wireless platform. Fob device 300 includes a housing 305containing the PCB representing metrological interface device 170.Accordingly, metrological interface device 170 is not visible in FIG.3A. Fob device 300 includes interface link 172 used to communicate witha metrological sensing device such as metrological sensing device 161(shown in FIG. 1C). In the exemplary embodiment, fob device 300 is incommunication with a pressure sensing device and receives asset data.Fob device 300 also includes a display 320 capable of displaying assetdata 325. In the exemplary embodiment, display 320 is a liquid crystaldisplay (“LCD”). In alternative embodiments, display 320 may include anydisplay capable of representing asset data 325. Alternately, display 320may display any information related to metrological interface device 170and connected metrological sensing device 161 including, withoutlimitation, power availability, signal strength, and connection status.

Fob device 300 also includes a control interface 330. In the exemplaryembodiment, control interface 330 includes a plurality of buttonscapable of controlling fob device 300. Control interface 330 can performfunctions including, without limitation, power activation anddeactivation, communication management, restart, and calibration ofasset data 325. Fob device 300 further includes LED display 335 capableof providing information related to fob device 300 including, withoutlimitation, communication link status and power status.

FIG. 3B is an illustration of an example hybrid device 300A containingmetrological interface device 170 (shown in FIG. 2) used to create auniversal wireless platform. Hybrid device 300A includes metrologicalsensing device 350 in communication with metrological interface device170 using interface link 172. In other words, hybrid device 300Aincludes a metrological sensing device 350 and metrological interfacedevice 170 in a shared housing 305A. As in fob device 300, hybrid device300A further includes display 320 configured to display asset data 325.Hybrid device 300A also includes controls 330 used to control hybriddevice 300A. Hybrid device 300A additionally includes LED display 335which is capable of providing information related to hybrid device 300Aincluding, without limitation, communication link status and powerstatus.

Accordingly, hybrid device 300A may provide value by assuring that aparticular metrological sensing device 350 is always capable ofcommunicating to a computing device such as mobile computing device 132(shown in FIG. 1A) using a wireless protocol such as BLE. Because hybriddevice 300A includes both metrological sensing device 350 andmetrological interface device 170 and hybrid device 300A is configuredso that they are in communication with one another, no additionalconfiguration is required.

FIG. 4 is a block diagram of a computing device 400 that may be used inmonitoring physical assets 140 (shown in FIG. 1C) by interacting withmetrological interface device 170 (shown in FIG. 2) using the universalwireless platform. Computing device 400 represents various forms ofdigital computers, such as laptops, desktops, workstations, personaldigital assistants, servers, blade servers, mainframes, and otherappropriate computers. Computing device 400 is also intended torepresent various forms of mobile devices, such as personal digitalassistants, cellular telephones, smart phones, and other similarcomputing devices. The components shown here, their connections andrelationships, and their functions, are meant to be examples only, andare not meant to limit implementations of the subject matter describedand/or claimed in this document.

In the exemplary embodiment, computing device 400 could be user mobilecomputing device 132 or any of monitoring server 180 and recordingcomputing device 181 (shown in FIG. 1C). Computing device 400 mayinclude a bus 402, a processor 404, a main memory 406, a read onlymemory (ROM) 408, a storage device 410, an input device 412, an outputdevice 414, and a communication interface 416. Bus 402 may include apath that permits communication among the components of computing device400.

Processor 404 may include any type of conventional processor,microprocessor, or processing logic that interprets and executesinstructions. Processor 404 can process instructions for executionwithin the computing device 400, including instructions stored in thememory 406 or on the storage device 410 to display graphical informationfor a GUI on an external input/output device, such as display 414coupled to a high speed interface. In other implementations, multipleprocessors and/or multiple buses may be used, as appropriate, along withmultiple memories and types of memory. Also, multiple computing devices400 may be connected, with each device providing portions of thenecessary operations (e.g., as a server bank, a group of blade servers,or a multi-processor system). In several examples embodiments, multiplecomputing devices 400 are used to receive, process, and communicateinformation related to field inspections of physical assets 140 (shownin FIG. 1C).

Main memory 406 may include a random access memory (RAM) or another typeof dynamic storage device that stores information and instructions forexecution by processor 404. ROM 408 may include a conventional ROMdevice or another type of static storage device that stores staticinformation and instructions for use by processor 404. Main memory 406stores information within the computing device 400. In oneimplementation, main memory 406 is a volatile memory unit or units. Inanother implementation, main memory 406 is a non-volatile memory unit orunits. Main memory 406 may also be another form of computer-readablemedium, such as a magnetic or optical disk.

Storage device 410 may include a magnetic and/or optical recordingmedium and its corresponding drive. The storage device 410 is capable ofproviding mass storage for the computing device 400. In oneimplementation, the storage device 410 may be or contain acomputer-readable medium, such as a floppy disk device, a hard diskdevice, an optical disk device, or a tape device, a flash memory orother similar solid state memory device, or an array of devices,including devices in a storage area network or other configurations. Acomputer program product can be tangibly embodied in an informationcarrier. The computer program product may also contain instructionsthat, when executed, perform one or more methods, such as thosedescribed above. The information carrier is a computer- ormachine-readable medium, such as main memory 406, ROM 408, the storagedevice 410, or memory on processor 404.

A high speed controller manages bandwidth-intensive operations for thecomputing device 400, while the low speed controller manages lowerbandwidth-intensive operations. Such allocation of functions is forpurposes of example only. In one implementation, the high-speedcontroller is coupled to main memory 406, display 414 (e.g., through agraphics processor or accelerator), and to high-speed expansion ports,which may accept various expansion cards (not shown). In theimplementation, low-speed controller is coupled to storage device 410and low-speed expansion port. The low-speed expansion port, which mayinclude various communication ports (e.g., USB, Bluetooth, Ethernet,wireless Ethernet) may be coupled to one or more input/output devices,such as a keyboard, a pointing device, a scanner, or a networking devicesuch as a switch or router, e.g., through a network adapter.

Input device 412 may include a conventional mechanism that permitscomputing device 400 to receive commands, instructions, or other inputsfrom a user such as field inspector 111, 112, 113, and 114 (shown inFIG. 1B) including visual, audio, touch, button presses, stylus taps,etc. Additionally, input device may receive location information.Accordingly, input device 412 may include, for example, a camera, amicrophone, one or more buttons, a touch screen, and/or a GPS receiver.Output device 414 may include a conventional mechanism that outputsinformation to the user, including a display (including a touch screen)and/or a speaker. Communication interface 416 may include anytransceiver-like mechanism that enables computing device 400 tocommunicate with other devices and/or systems. For example,communication interface 416 may include mechanisms for communicatingwith another device or system via a network.

As described herein, computing device 400 facilitates the use of auniversal wireless platform to obtain asset data from metrologicalsensing devices via metrological interface devices. Computing device 400further facilitates dynamic workflow processing and thereby thecollection, review, and processing of asset data. Computing device 400may perform these and other operations in response to processor 404executing software instructions contained in a computer-readable medium,such as memory 406. A computer-readable medium may be defined as aphysical or logical memory device and/or carrier wave. The softwareinstructions may be read into memory 406 from another computer-readablemedium, such as data storage device 410, or from another device viacommunication interface 416. The software instructions contained inmemory 406 may cause processor 404 to perform processes describedherein. Alternatively, hardwired circuitry may be used in place of or incombination with software instructions to implement processes consistentwith the subject matter herein. Thus, implementations consistent withthe principles of the subject matter disclosed herein are not limited toany specific combination of hardware circuitry and software.

The computing device 400 may be implemented in a number of differentforms, as shown in the figure. For example, it may be implemented as astandard server, or multiple times in a group of such servers. It mayalso be implemented as part of a rack server system. In addition, it maybe implemented in a personal computer such as a laptop computer. Each ofsuch devices may contain one or more of computing device 400, and anentire system may be made up of multiple computing devices 400communicating with each other.

The processor 404 can execute instructions within the computing device400, including instructions stored in the main memory 406. The processormay be implemented as chips that include separate and multiple analogand digital processors. The processor may provide, for example, forcoordination of the other components of the computing device 400, suchas control of user interfaces, applications run by computing device 400,and wireless communication by computing device 400.

Computing device 400 includes a processor 404, main memory 406, ROM 408,an input device 412, an output device such as a display 414, acommunication interface 416, among other components including, forexample, a receiver and a transceiver. The computing device 400 may alsobe provided with a storage device 410, such as a microdrive or otherdevice, to provide additional storage. Each of the components areinterconnected using various buses, and several of the components may bemounted on a common motherboard or in other manners as appropriate.

Computing device 400 may communicate wirelessly through communicationinterface 416, which may include digital signal processing circuitrywhere necessary. In the exemplary embodiment, communication interface416 provides for communication using Bluetooth® Low Energy (“BLE”) orBluetooth SMART®. Communication interface 416 may also provide forcommunications under various modes or protocols, such as 802.11b,ZigBee®, GSM voice calls, SMS, EMS, or MMS messaging, CDMA, TDMA, PDC,WCDMA, CDMA2000, or GPRS, among others. Such communication may occur,for example, through radio-frequency transceiver. In addition,short-range communication may occur, such as using a Bluetooth®, WiFi,or other such transceiver (not shown). In addition, a GPS (GlobalPositioning system) receiver module may provide additional navigation-and location-related wireless data to computing device 400, which may beused as appropriate by applications running on computing device 400.

FIG. 5 is an exemplary process flow of a system implemented 500 bymobile computing device 132 interacting with a metrological sensingdevice 540 using the universal wireless platform and, more specifically,metrological interface device 170. FIG. 5 illustrates a simplified modelof the use of the universal wireless platform in system 500 to explainthe interaction between metrological sensing device 540, metrologicalinterface device 170, and mobile computing device 132 using theplatform. Although only one user 510, one mobile computing device 132,one physical asset 530, one metrological sensing device 540, oneinterface link 172, and one metrological interface device 170 are shown,the universal wireless platform can facilitate any number of eachcomponent. Note that, as described below, interactions may change whenadditional components are introduced.

In the exemplary embodiment, system 500 includes a user 510, such asfield inspector 111 (shown in FIG. 1C), using mobile computing device132 to conduct asset monitoring and inspection tasks. System 500 alsoincludes physical asset 530 which is measured by metrological sensingdevice 540. In the exemplary embodiment, physical asset 530 is apressure vessel and metrological sensing device 540 is a pressure meter.In other embodiments, physical asset 530 may be any kind of physicalasset and metrological sensing device 540 may be any sensor or devicecapable of collecting asset data regarding physical asset 530 andinteracting with metrological interface device 170 via interface link172. System 500 also includes metrological interface device 170communicating with metrological sensing device 540 via interface link172. In the exemplary embodiment, metrological interface device 170 isfob device 300 (shown in FIG. 3A) communicating with metrologicalsensing device 540 using I2C protocol. In other embodiments,metrological interface device 170 may be contained in hybrid device 300A(shown in FIG. 3B) and communicate with metrological sensing device 540using any communication protocol.

In operation, metrological interface device 170 advertises 572availability for connection using a wireless protocol. In the exemplaryembodiment, metrological interface device 170 uses BLE module 230 (shownin FIG. 2) to advertise 572 availability using Bluetooth® Low Energy. Asused herein, “advertising” refers to a substantially persistentcommunication by a device, such as metrological interface device 170,indicating that the device is available for connection andcommunication. In some examples, metrological interface device 170 mayadvertise in a private mode. The private mode allows only computingdevices 132 with pre-existing identifying information for metrologicalinterface device 170 to detect the advertised 572 availability of themetrological interface device 170.

User 510 requests mobile computing device 132 to scan 574 foravailability of metrological interface devices 170. Scan 574 detects allavailable assets 573 which have been advertised 572 by metrologicalinterface devices 170. Accordingly, available assets 573 refer tometrological interface devices 170 which are advertising availability.Available assets 573 are reported back to mobile computing device 132 asidentified available assets 575. In at least some examples, scan 574detects available assets 573 only within a particular physical range ofmobile computing device 132. In some additional examples, physical rangemay be determined by the strength of signal between mobile computingdevice 132 and metrological interface device 170. Accordingly, althougha particular metrological interface device 170 may be advertisingavailability, mobile computing device 132 may not be able to identify575 the availability because of physical distance, physicalobstructions, and/or weak signal strength.

User 510 can view all identified available assets 575 on mobilecomputing device 132 and select a particular identified available asset575 to connect with. Upon selection, mobile computing device 132requests a connection 576 with metrological interface device 170.Requesting a connection 576 may require the use of encryption, securitykeys, and permissions. Such measures allow for greater security of data,including asset data, collected by metrological interface device 170. Ifsuch permissions, encryptions, and security keys are successfully usedand satisfied, mobile computing device 132 and metrological interfacedevice establish a connection 577. In the exemplary embodiment, theconnection created on establishing a connection 577 is an “active”connection. In the exemplary embodiment, an active connection, as usedherein, allows mobile computing device 132 to send and receive data,including asset data, to and from metrological interface device 170.Further, in the exemplary embodiment, the active connection is anexclusive connection which means that no other mobile computing device132 may simultaneously access metrological interface device 170.Exclusivity allows for reduced redundant data being collected by users510 and reduces the unnecessary use of metrological interface device170. Reduction in unnecessary use of metrological interface device 170substantially facilitates conserving power in metrological interfacedevice 170. It should be noted that an exclusive active connection meansthat metrological interface device 170 can only connect to one mobilecomputing device 132. However, mobile computing device 132 can connectto a plurality of metrological interface devices 170. In otherembodiments, metrological interface device 170 may have non-exclusiveconnections in an active connection.

In some examples, the connection formed by establishing a connection 577may be a “dormant” connection. A dormant connection may retain theexclusivity of the active connection while no communication occursbetween metrological interface device 170 and mobile computing device132. A dormant connection may be established if one of mobile computingdevice 132 and/or metrological interface device 170 determine that achange has occurred in the connection state. A change in connectionstate may be indicated by the signal strength falling below a signalstrength threshold, communication frequency between metrologicalinterface device 170 and mobile computing device 132 falling below acommunication interval threshold, an elapsed period between metrologicalinterface device 170 and mobile computing device 132 exceeding a totalconnection time limit, and remaining batter life in metrologicalinterface device 170 decreasing below a battery life threshold.Alternately, a change in connection state may cause the connection to bereleased. Releasing a connection causes an active connection to beterminated and resultantly prevents any communication betweenmetrological interface device 170 and mobile computing device 132without regenerating an active connection. Releasing a connection alsocauses metrological interface device 170 to begin advertisingavailability 572.

Upon establishing connection 577, mobile computing device 132 canadditionally communicate 578 with metrological interface device 170.Communicating 578 represents sending and receiving data including assetdata. In other words, upon establishing connection 577, mobile computingdevice 132 can receive asset data corresponding to the physical state ofphysical asset 530 as detected by metrological sensing device 540 andtransmitted to metrological interface device 170 using interface link172. Communication 578 also represents sending instructions tometrological interface device 170. For example, in the exemplaryembodiment, user 510 viewing mobile computing device 132 may determinethat asset data transmitted from metrological interface device 170appears to be anomalous. User 510 may request mobile computing device132 to transmit a calibration request to metrological interface device170 causing a calibration process to be run on processor 220 (shown inFIG. 2).

Mobile computing device 132 includes software designed to facilitatesystem 500. Many known types of mobile computing devices 132 exist andare associated with many known types of operating systems, physicalhardware, and associated configurations. The software designed tofacilitate system 500 is designed with a flexible architecture which maybe deployed on a plurality of types of mobile computing devices 132 andover a plurality of associated operating systems and hardware types.Accordingly, as metrological interface device 170 substantially allowsfor a universal wireless platform and enables a plurality of types ofmetrological sensing devices 540 to transmit data to computing devicesincluding mobile computing devices 132, the software design associatedwith system 500 substantially allows for a plurality of types of mobilecomputing devices 132 to interact with the universal wireless platform.Additionally, the software facilitating system 500 similarly may supportany computing devices 400 (shown in FIG. 4).

FIG. 6 is an exemplary process flow of a system 600 implemented bymobile computing device 132 interacting with a metrological sensingdevice 640 using the universal wireless platform and, more specifically,metrological interface device 170 to facilitate efficient asset datacollection, asset monitoring, and asset inspection.

As in FIG. 5, FIG. 6 includes a user, field inspector 610, using amobile computing device 132 to inspect and monitor physical asset 630.Physical asset 630 is monitored by metrological sensing device 640. Inthe exemplary embodiment, physical asset 630 is a pressure vessel 630and metrological sensing device 640 is a pressure meter. In otherembodiments, physical asset 630 may be any kind of physical asset andmetrological sensing device 640 may be any sensor or device capable ofcollecting asset data regarding physical asset 630 and interacting withmetrological interface device 170 via interface link 172.

System 600 also includes a plurality of computing devices in networkedcommunication with mobile computing device 132. In the exemplaryembodiment, computing including tablets 621, laptops 622, and servers623. Computing devices 621, 622, and 623 function as cloud resources 690and can resultantly function as secondary processing resources to mobilecomputing device 132. Cloud resources 690 including computing devices621, 622, and 623 can also provide data to mobile computing device 132.Cloud resources 690 including computing devices 621, 622, and 623 areexamples of generic computing device 400 (shown in FIG. 4). Computingdevices 621, 622, and 623 are respectively associated with users 611,612, and 613. Users 611, 612, and 613 may be used to facilitateprocessing and analysis described. Additionally, input received from auser such as users 611, 612, and 613 at computing devices 621, 622, and623 may be used to facilitate processing and analysis. In other words,processing and analysis may substantially incorporate expert user datafrom users such as users 611, 612, and 613. Alternately, processing andanalysis may apply algorithms including heuristic algorithms usingcomputing devices 621, 622, and 623.

As in FIG. 5, the software designed to facilitate system 600 similarlyis designed for a plurality of types of computing devices includingmobile computing device 132. Accordingly, the software facilitatesinteraction with a plurality of operating systems and hardwarearchitectures for a plurality of mobile computing devices 132.Additionally, the software facilitating system 600 similarly may supportany computing devices 400 (shown in FIG. 4).

In operation, mobile computing device 132 has an established connection577 (shown in FIG. 5) with metrological interface device 170 and iscapable of communicating 578 (shown in FIG. 5). Mobile computing device132 requests 673 a metrological data set, or asset data set 674. Assetdata set 674 represents at least one asset data measured by metrologicalsensing device 640 and transmitted to metrological interface device 170using interface link 172. Asset data set 674 is sent to mobile computingdevice 132 by metrological interface device 170 using a wirelessprotocol. Asset data set 674 may represent primary asset data (i.e.,asset data representing physical characteristics of physical asset 630)or secondary asset data (i.e. asset data which may be processed intoprimary asset data). In the exemplary embodiment, physical asset 630 isa pressure vessel and metrological sensing device 640 is a pressuresensor. Accordingly, asset data set 674 describes a plurality ofpressure readings associated with pressure vessel 630.

Cloud resources 690 (including computing device 621, 622, and 623)and/or mobile computing device 132 additionally store asset model 675 ata memory device, such as memory device 406 (shown in FIG. 4). Assetmodel 675 reflects a state of physical asset 630 based upon historicallyavailable asset data. In other words, asset model 675 represents a stateof physical asset 630 without considering presently received asset dataset 674. Asset model 675 describes the expected conditions and,therefore, the expected asset data associated with physical asset 630based upon factors including the age, usage, and conditions of physicalasset 630. Accordingly, inspection and monitoring of physical asset 630involves a comparison between asset data set 674 and asset model 675. Inthe exemplary embodiment, asset model 675 describes a predictedcondition of pressure vessel 630 and a predicted pressure readingexpected to be received from metrological sensing device 640 in assetdata set 674.

Asset data set 674 is processed with asset model 675 into a processedasset data set to determine a disposition 676. This processing step mayadditionally include processing asset data set 674 from secondary assetdata into primary asset data using mobile computing device 132 and/orcloud resources 690. Further, depending on the availability of cloudresources 690 and the processing ability of mobile computing device 132,mobile computing device 132 either determines a disposition 676 locally(i.e., using mobile computing device 132) or requests that cloudresources 690 process disposition 676. Disposition 676 substantiallyrepresents determining whether asset data set 674 is predicted by assetmodel 675 or alternately determining whether asset data set 674indicates a variance between asset model 675 and asset data set 674. Inthe exemplary embodiment, determining disposition 676 representscomparing the expected pressure reading of pressure vessel 630 basedupon asset model 675 to the actual pressure reading received frommetrological sensing device 640 in asset data set 674. If there is avariance, it may suggest that asset data set 674 is inaccurate or assetmodel 675 is inaccurate. Accordingly, additional readings may be usefulto determine the presence of an anomaly. Alternately, if there is novariance, it may suggest that asset model 675 is accurate and fieldinspector 610 may not need to continue inspecting pressure vessel 630.In more complex examples, such rapid reconciliation between asset model675 and asset data set 674 may make field inspections substantially moreefficient. When a variance exists in disposition 676, field inspector610 may take additional readings as asset data set 674 and efficientlyupdate or replace asset model 675. Alternately, when no variance isdetermined to exist in disposition 676, field inspector 610 may reducethe expenditure of time and resources on field inspection by ceasing afield inspection at an earlier point than possible without the use ofthe system and method described.

If disposition 676 indicates that asset data set 674 is predicted byasset model 675, mobile computing device 132 generates report 678.Report 678 will be transmitted to at least one report recipientincluding, without limitation, mobile computing device 132, cloudresources 690, field inspector 610 and users 611, 612, 613. Report 678may be transmitted using any suitable protocol including, withoutlimitation, email, SMS, database update, file transfer, and physicaltransmission of a physical file.

If disposition 676 indicates that asset data set 674 is not predicted byasset model 675, mobile computing device may alternately recalibrate orupdate asset model 675 or request 673 asset data set 674 again. In theexemplary embodiment, when pressure readings from asset data set 674 areinconsistent with asset model 675, more readings may be required. In atleast some examples, it may be important to confirm whether asset model675 is actually inaccurate. For example, transient conditions orinconsistent metrological sensing devices 640 may cause asset data set674 to produce a variance in disposition 676 for a brief period.Accordingly, some inspections may require multiple confirmations thatasset data set 674 is in variance with asset model 675. Once a varianceis sufficiently confirmed, asset model 675 may be updated. In otherexamples, however, asset model 675 may be immediately updated upondetermining a variance. For example, if asset data set 674 is known tobe simple and reliable (e.g., a physical measurement of width for a newmetrological sensing device 640), it may be inefficient to take multiplereadings and asset model 675 may be updated with no request for newasset data set 674.

Updating asset model 675 represents processing at least one asset dataset 674 and asset model 675 to determine a new asset model. Given thecomputational complexity that may be required for updating at least someasset models 675, cloud resources 690 may be utilized for such updating.

During the workflow illustrated in FIG. 6, field inspector 610 may seekadditional external input from human users including, for example, users611, 612, and 613, and data sources associated with, for example, cloudresources 690. Accordingly, the software system provides tools whichfacilitate interaction between field inspector 610 and users 611, 612,and 613 including, without limitation, messaging and chat software.Similarly, the software system provides tools which facilitate queryingcloud resources 690.

FIG. 7 is an exemplary method 700 performed by a mobile computing device132 (shown in FIG. 5) communicating with a metrological interface device170 (both shown in FIG. 5) using the universal wireless platform.

Mobile computing device 132 scans 710 for available metrologicalinterface devices 170. Scanning 710 substantially represents mobilecomputing device 132 using wireless protocols including Bluetooth® LowEnergy to identify metrological interface devices 170 that areadvertising availability 572 as available assets 573 and are accordinglyidentified available assets 575 (shown in FIG. 5).

Mobile computing device 132 transmits 720 a connection request to atleast one of the available metrological interface devices. Transmitting720 substantially represents mobile computing device 132 requesting aconnection 576 (shown in FIG. 5) to at least one metrological interfacedevice 170.

Mobile computing device 132 creates 730 an active connection with the atleast one available metrological interface device. Creating 730 anactive connection represents mobile computing device requesting 576(shown in FIG. 5) a connection with one of the identified availableassets 575 and establishing 577 a connection.

Mobile computing device 132 communicates 740 with at least oneconnecting metrological interface device. Communicating 740 representsmobile computing device 132 communicating with metrological interfacedevice 170 after establishing connection 577.

FIG. 8 is an exemplary method 800 performed by a mobile computing device132 communicating with a metrological interface device 170 and aplurality of cloud based resources 690 (all shown in FIG. 6) using theuniversal wireless platform.

Mobile computing device 132 initially receives 810 a metrological dataset from a metrological interface device. Receiving 810 representsmobile computing device 132 receiving asset data set 674 afterrequesting 673 asset data set 674 (both shown in FIG. 6). Asset data set674 includes asset data detected by metrological sensing device 640(shown in FIG. 6) and transmitted to metrological interface device 170.

Mobile computing device 132 processes the metrological data set and anasset model into a processed metrological data set. Processing 820represents mobile computing device 132 requesting asset model 675 (shownin FIG. 6) from at least one of memory device 406 (shown in FIG. 4)associated with mobile computing device and memory devices 406associated with cloud based resources 690 and comparing the predictedasset data set to asset data set 674. In at least some embodiments,mobile computing device 132 uses cloud based resources 690 to process820 asset data set 674 and asset model 675.

Processing 820 may result in the determination of an inconsistency, ormetrological variance, in processed metrological data set. Upondetermining such metrological variance, mobile computing device 132recalibrates 830 the asset model and receives 810 a metrological dataset from a metrological interface device. In other words, when ametrological variance is determined, asset model 675 may be adjusted anda new asset data set 674 is requested and received to confirm therecalibrated asset model 675.

Upon determining no metrological variance, computing device 132 reports840 the metrological data set and the asset model to at least one reportrecipient. Reporting 840 represents transmitting report 678 (shown inFIG. 6) to at least one report recipient including, without limitationmobile computing device 132, cloud resources 690, field inspector 610and users 611, 612, 613 (all shown in FIG. 6).

FIG. 9 is a diagram of components of one or more example computingdevices that may be used in the environment shown in FIGS. 5 and 6.

For example, one or more of computing devices 400 may be used to processtransmit and process asset data sets 674 and asset models 675 (shown inFIG. 6). Computing devices 400 may include mobile computing devices 132(shown in FIGS. 5 and 6) and cloud resources 690 (shown in FIG. 6). FIG.9 further shows a configuration of database 920 which may be incommunication with any computing device 400. Database 920 is coupled toseveral separate components within computing device 400 and includesinformation which perform specific tasks.

Computing device 400 includes a scanning component 902 for scanning 710(shown in FIG. 7) for available metrological interface devices 170(shown in FIG. 2). Computing device 400 further includes a transmittingcomponent 903 for transmitting 720 (shown in FIG. 7) a connectionrequest to at least one of the available metrological interface devices.Computing device 400 also includes creating component 904 for creating730 (shown in FIG. 7) an active connection with the at least oneavailable metrological interface device. Computing device 400additionally includes communicating component 905 for communicating 740(shown in FIG. 7) with at least one connecting metrological interfacedevice. Computing device 400 further includes receiving component 906for receiving 810 (shown in FIG. 8) a metrological data set from ametrological interface device. Computing device 400 also includesprocessing component 907 for processing 820 (shown in FIG. 8) themetrological data set and an asset model into a processed metrologicaldata set. Computing device 400 additionally includes recalibratingcomponent 908 for recalibrating 830 (shown in FIG. 8) the asset model.Computing device 400 moreover includes reporting component 909 forreporting 840 (shown in FIG. 8) report 678 (shown in FIG. 6) to at leastone report recipient including, without limitation mobile computingdevice 132, cloud resources 690, field inspector 610 and users 611, 612,613 (all shown in FIG. 6).

In an exemplary embodiment, database 920 is divided into a plurality ofsections, including but not limited to, a data modeling section 910, analgorithms section 912, a heuristics section 914, a communicationsprotocol and management section 916, and an applications section 918.These sections within database 120 are interconnected to update andretrieve the information as required. Data modeling section 910 mayinclude data models. Algorithms section 912 may include algorithms forprocessing and analyzing asset data. Heuristics 914 may include programsand functions to solve questions related to asset data. Communicationand protocol management section 916 may include information and policiesregarding the communication over the universal wireless platform.Applications section 918 may include information related to theapplications and distributions and versions of applications tofacilitate the systems and methods described.

The above-described computer-implemented systems and methods provide anefficient approach for inspecting and monitoring physical assets using auniversal wireless platform. The systems and methods create suchefficiency by providing a metrological interface device capable ofreceiving data from a plurality of metrological sensing devices andtransmitting data to a plurality of computing devices. The embodimentsdescribed herein also reduce communication and logistics costsassociated with poorly timed or coordinated decisions. Specifically, bycollecting data described above efficiently, limited effort is spent ondata collection and physical interaction with metrological sensingdevices is minimized. Therefore, the issues which may arise without suchan approach are minimized. Also, the methods and systems describedherein increase the utilization of resources in monitoring andinspection tasks. Specifically, by taking such a coordinated,cloud-based approach, resources utilization is enhanced. Further, themethods and systems described herein improve capital and human resourceexpenditure through enhanced coordinated activities.

An exemplary technical effect of the methods and computer-implementedsystems described herein includes at least one of (a) increased fieldinspection of physical assets; (b) increased speed of analysis of assetdata; and (c) improved response times for diagnostics and maintenance ofphysical assets.

Exemplary embodiments for facilitating a universal wireless platform foruse in inspection and monitoring is described above in detail. Thecomputer-implemented systems and methods of operating such systems arenot limited to the specific embodiments described herein, but rather,components of systems and/or steps of the methods may be utilizedindependently and separately from other components and/or stepsdescribed herein. For example, the methods may also be used incombination with other enterprise systems and methods, and are notlimited to practice with only the inspection and monitoring functions asdescribed herein. Rather, the exemplary embodiment can be implementedand utilized in connection with many other enterprise applications.

Although specific features of various embodiments of the invention maybe shown in some drawings and not in others, this is for convenienceonly. In accordance with the principles of the invention, any feature ofa drawing may be referenced and/or claimed in combination with anyfeature of any other drawing.

This written description uses examples to disclose the invention,including the best mode, and also to enable any person skilled in theart to practice the invention, including making and using any devices orsystems and performing any incorporated methods. The patentable scope ofthe invention is defined by the claims, and may include other examplesthat occur to those skilled in the art. Such other examples are intendedto be within the scope of the claims if they have structural elementsthat do not differ from the literal language of the claims, or if theyinclude equivalent structural elements with insubstantial differencesfrom the literal language of the claims.

What is claimed is:
 1. A computer-implemented system comprising: aplurality of metrological interface devices, each said plurality ofmetrological interface devices comprising a printed circuit board (PCB)comprising at least one metrological sensor communication interface, andat least one first wireless communication interface, wherein each saidplurality of metrological interface devices is in communication with arespective metrological sensing device via said at least onemetrological sensor communication interface, wherein each respectivemetrological sensing device is configured to detect metrological datafrom a physical asset, each said plurality of metrological interfacedevices is configured to receive the metrological data from therespective metrological sensing device; and a plurality of mobilecomputing devices, each said plurality of mobile computing devicecomprising a memory device, a processor coupled to said memory device,and a second wireless communication interface coupled to said memorydevice and to said processor, wherein said second wireless communicationinterface is configured to communicate with said plurality ofmetrological interface devices via said first wireless communicationInterface, wherein each mobile computing device of said plurality ofmobile computing devices is a heterogeneous mobile computing device andis configured to: scan for available metrological interface devices ofsaid plurality of metrological interface devices, wherein the availablemetrological interface devices are a subset of said plurality ofmetrological interface devices; transmit a connection request to atleast one of the available metrological devices to connect to the atleast one of the available metrological devices; create an activeconnection with the at least one of the available metrological interfacedevices; store, at said memory device, at least one analyticalapplication, the at least one analytical application programmed to runon the heterogeneous mobile computing device; and analyze metrologicaldata, at said memory device, using the at least one analyticalapplication; communicate with the connected said at least one of theavailable metrological interface devices to receive the metrologicaldata that is to be analyzed, wherein each of said plurality ofmetrological interfaces is configured to: advertise connectionavailability to said plurality of mobile computing devices; receive aconnection request from a connecting mobile computing device of theplurality of mobile computing devices; and stop advertising connectionavailability to remaining said plurality of mobile computing devices,wherein the at least one analytical application is designed based on aset of application programming interface (API) libraries associated withconnecting to said plurality of metrological interface devices; whereinthe set of API libraries allow the at least one analytical applicationto provide substantially similar features of said connected to at leastone of the available metrological interface devices on the heterogeneousmobile device that has created the active connection with the at leastone of the available metrological interface devices.
 2. Thecomputer-implemented system in accordance with claim 1, wherein eachsaid first wireless communication interface and each said secondwireless communication interface is configured to communicate usingprotocols including at least one of Bluetooth low energy (BLE) andwireless local area network protocols.
 3. The computer-implementedsystem in accordance with claim 1, wherein each said PCB is configuredto interface with said respective metrological sensing device via the atleast one metrological sensor communication interface using a standardinterface protocol including at least one of universal serial bus (USB),recommended standard 232 (RS232), Inter-Integrated Circuit (I2C), serialperipheral interface bus (SPI), analog, and a generic I/O interface. 4.The computer-implemented system in accordance with claim 1, wherein eachof said plurality of mobile computing devices is configured to establisha data connection to a plurality of said plurality of metrologicalinterface devices, substantially simultaneously.
 5. Thecomputer-implemented system in accordance with claim 1, wherein saidplurality of mobile computing devices are mobile computing devicesincluding at least one of a tablet computer, a smartphone, and aphablet.
 6. The computer-implemented system in accordance with claim 1,wherein each respective metrological sensing device is coupled to aphysical asset, and each of said plurality of metrological interfacedevices is further configured to: receive, from the respectivemetrological sensing device via said at least one metrological sensorcommunication interface, metrological data substantially representingphysical measurement data associated with the physical asset.
 7. Thecomputer-implemented system in accordance with claim 1, wherein each ofsaid plurality of metrological devices further comprises a chassissubstantially housing said PCB.
 8. The computer-implemented system inaccordance with claim 7, wherein each of said plurality of metrologicalinterface devices is coupled to the respective metrological sensingdevice and enclosed within the chassis.
 9. The computer-implementedsystem in accordance with claim 1, wherein each of said plurality ofmobile computing devices stores an asset model and is configured tocompare metrological data received from the at least one of theavailable metrological interface devices to the asset model.
 10. Thecomputer-implemented system in accordance with claim 9, wherein each ofsaid plurality of mobile computing devices is configured to update theasset model based on the metrological data received from the at leastone of the available said metrological interface devices.
 11. Thecomputer-implemented system in accordance with claim 1, wherein each ofsaid plurality of mobile computing devices is further configured to: a)receive a metrological data set that substantially represents dataassociated with the physical asset at a point in time; b) process, bysaid processor, the metrological data set and an asset data model into aprocessed metrological data set that substantially represents a model ofthe physical asset associated with the metrological sensing device andfurther associated with said metrological interface device receiving themetrological data set that substantially represents data associated withthe physical asset at the point in time; c) upon determining, based onthe processed metrological data set, a metrological variance,recalibrated the asset data model and return to step (a); and d) upondetermining no metrological variance, report the metrological asset datamodel to at least one report recipient.
 12. The computer-implementedsystem in accordance with claim 11, wherein each of said plurality ofmobile computing devices is configured to: process the metrological dataset and the asset data model into the processed metrological data setusing at least one networked computing resource associated with saidmobile computing device processing the metrological data set and theasset model.
 13. The computer-implemented system in accordance withclaim 11, wherein each of said plurality of mobile computing devices isconfigured to: process the metrological data set from a secondarymetrological data set into a primary metrological data set, wherein thesecondary metrological data set represents a second set of dataassociated with the physical asset which does not represent a physicalstate of the physical asset and the primary metrological data setrepresents a first set of data associated with the physical asset whichrepresents the physical state of the physical asset.
 14. Thecomputer-implemented system in accordance with claim 11, wherein each ofsaid plurality of mobile computing devices is configured to process themetrological data set by applying at least one of heuristic algorithmsand expert-user input.
 15. The computer-implemented system in accordancewith claim 1, wherein each of said metrological interface devices isfurther configured to: determine whether a connection state to aconnected one of said plurality of mobile computing devices has changed;release the connection to the connected one of said plurality of mobilecomputing devices; and resume advertising availability to said pluralityof mobile computing devices.
 16. The computer-implemented system inaccordance with claim 1, wherein each of said metrological interfacedevices is further configured to: determine whether a connectioncondition to a connected one of said plurality of mobile computingdevices has changed; and change a data connection to the connected oneof said plurality of mobile computing devices from an active connectionto a dormant connection, the dormant connection substantiallyrepresenting a connection where data communication is halted and lessenergy is consumed than in an active connection.
 17. Thecomputer-implemented system in accordance with claim 1, wherein saidplurality of mobile computing devices are configured to communicate withsaid plurality of metrological interface devices by at least one of:requesting metrological data from at least one metrological interfacedevice of said plurality of metrological interface devices; calibratingsaid at least one metrological interface device; and receivingmetrological data from said at least one metrological interface device.18. The computer-implemented system in accordance with claim 1, whereineach of said plurality of metrological interface devices has firmwareencoded in said PCB, wherein the firmware governs at least one ofcommunication protocols, interface protocols, encryption, data formats,and power management.